Skip to content

Fix Celery tests after conf-backcompat merge#64388

Merged
jscheffl merged 1 commit intoapache:mainfrom
jscheffl:bugfix/fix-celery-tests-after-conf-backcompat-merge
Mar 29, 2026
Merged

Fix Celery tests after conf-backcompat merge#64388
jscheffl merged 1 commit intoapache:mainfrom
jscheffl:bugfix/fix-celery-tests-after-conf-backcompat-merge

Conversation

@jscheffl
Copy link
Copy Markdown
Contributor

It seems after merging of #64292 the pytests of Celery are failing because default provider config is not loaded anymore. This PR fixes the pytest as default config missing.


Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

@Nataneljpwd
Copy link
Copy Markdown
Contributor

Nataneljpwd commented Mar 29, 2026

Tests seem to fail due to failed uv install (cache lock timeout), maybe it is a good idea to use no cache when building both with and without constraints at the same time?
It happens specifically on the iceberg-core package, I will investigate further
Or maybe increase the lock timeout of uv
What do you think?

@gopidesupavan gopidesupavan force-pushed the bugfix/fix-celery-tests-after-conf-backcompat-merge branch from 7a28571 to e5be536 Compare March 29, 2026 14:27
@jscheffl jscheffl merged commit 1169ef3 into apache:main Mar 29, 2026
90 checks passed
@jscheffl
Copy link
Copy Markdown
Contributor Author

Ah, no backport needed :-D

@jscheffl jscheffl removed backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch backport-to-v3-1-test labels Mar 29, 2026
@github-actions github-actions bot added this to the Airflow 3.1.9 milestone Mar 29, 2026
@github-actions
Copy link
Copy Markdown

Hi maintainer, this PR was merged without a milestone set.
We've automatically set the milestone to Airflow 3.1.9 based on: backport label targeting v3-1-test
If this milestone is not correct, please update it to the appropriate milestone.

This comment was generated by Milestone Tag Assistant.

github-actions bot pushed a commit that referenced this pull request Mar 29, 2026
(cherry picked from commit 1169ef3)

Co-authored-by: Jens Scheffler <95105677+jscheffl@users.noreply.github.com>
github-actions bot pushed a commit that referenced this pull request Mar 29, 2026
(cherry picked from commit 1169ef3)

Co-authored-by: Jens Scheffler <95105677+jscheffl@users.noreply.github.com>
@github-actions
Copy link
Copy Markdown

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-2-test PR Link

@github-actions
Copy link
Copy Markdown

Backport successfully created: v3-1-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-1-test PR Link

@jscheffl jscheffl removed this from the Airflow 3.1.9 milestone Mar 29, 2026
nailo2c pushed a commit to nailo2c/airflow that referenced this pull request Mar 30, 2026
Suraj-kumar00 pushed a commit to Suraj-kumar00/airflow that referenced this pull request Apr 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants